This forum is closed to new posts and
responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:
How could you have a row for a doc that's no longer there?
We opted to disallow any deletions from an app, EVER. Each app includes a 'hide' or 'remove' function that sets a field (Hide) to a value (Hidden) and all view selections exclude them except the admin view called 'hidden docs'. In some apps, we require entry of a reason for hiding a doc and possibly even an eSig.
This way, we can recover docs removed in error. Generally, the overhead ('extra' docs) is trivial and never been a real problem for us.
If we have an app were deletion makes sense but we don't want to allow direct deletion, we use the 'hide' method and then run a scheduled agent once a week to do the actual deletion of the doc. If we needed a marker/tombstone, we'd created it at this event.
If this seems like overkill:
We started using this in R4 when soft deletes didn't exist and have never seen a need to change the designs.
We work in a highly regulated environment where record histories are mandatory so in addition to the 'no delete' rule, we also use the OpenNTF 'Audit Manager'.
Feedback response number WEBB8ZBP5B created by ~Hank Lopvelutergon on 10/22/2012